Known Issues in Helix QAC 2024.4

The following list summarizes extant issues within GUI and CLI of Helix QAC 2024.4.

  • It is not possible to upload results to Validate using Helix QAC 2023.1 to a project that has been configured with Helix QAC 2023.2. The upload will fail with an error.
  • When viewing a component (or compliance manual) from within the Help system in qagui, clicking on the “Contents” link within the manual will navigate back to a page showing the various available manuals for that component. Use the Contents link from the left of the qagui Help panel to navigate to the actual contents page for the component.
  • Reprise Server. If you are not accessing a Reprise Server v11.x or later then a connection cannot be made using "localhost". In this case, you should specify 127.0.0.1 instead of "localhost".
  • Adding 1.0.5 components to the component search path causes rule groups and messages to appear empty for version 2.0.1 projects. Please do not mix 1.0.5 components and 2.0.1 components.
  • Windows Firewall will ask you if the Helix QAC Database Daemon, QAXD, should be allowed access to the computer’s network connections. Please ensure that, as a minimum, QAXD is given permission to access Private Networks.
  • Under Linux, if QT software is installed under the "/opt" folder, Helix QAC will not be able to run an analysis.
  • Under Linux, if there are one or more spaces in the name of the Helix QAC installation directory, e.g "Helix QAC 2.5.0", then it is not possible to generate a Version Control System baseline.
  • Manually editing the Helix QAC configuration file qa-framework-app.xml may lead to program startup problems if the modifications are not correct. We recommend that qa-framework-app.xml is edited using the Helix QAC tools.
  • It is not possible to create a custom component for Helix QAC.
  • It is not possible to apply suppressions to a Unified project that has been created by downloading a project definition.
  • Projects with single or multiple configurations are allowed to upload their analysis results to either Dashboard or Validate. However any project that is or will be unified (in Dashboard) or connected (in Validate) can only have a single configuration.
  • The Dashboard server will not operate correctly with Unified projects that are derived from Helix QAC and have been named using the Unicode character set.
  • In Dashboard, the case sensitivity of a Unified Project Name with Snapshots may be lost.
  • QA·CLI View options -N and -O only work correctly if the RCMA that is in the toolchain is not in the CMA Projects list.
  • If the User Messages File location is changed from the default, then the component messages from Dashboard are not downloaded.
  • If you are operating Helix QAC with multiple versions of the same component, then the User Message that was created for a specific version of the component will also appear with other versions of the same component.
  • If a suppression justification message is modified following analysis, then the code file should be cleaned prior to the next analysis. Otherwise, a warning message will be displayed, stating "Unexpected number of suppression details".
  • After a User Message has been added with an RCF Rule Group, and an analysis is then performed, the GUI will not show the rule or message group in the Analysis/Results Diagnostics panel. Restarting the GUI will resolve this problem.
  • A Helix QAC Project created in version 1.0.4 or earlier will not be initially functional with Framework 2.1.3. This is because the Project XML file, prqaproject.xml, has missing data that is required by Framework 2.1.3. To fix this, please include one of the following lines within the <configuration >XML element of the prqaproject.xml, depending on your programming language:

    • – C or C++: <languageFamily name="C/C++"/ >

  • The default memory allocator used by Helix QAC is now mimalloc (https://github.com/microsoft/mimalloc). This allocator has been shown to address some rare non-deterministic failures. If analysis finishes with "Unknown Error" (to date, only seen on Windows 7 systems), then you can set the environment variable MIMALLOC_DISABLE_REDIRECT to 1 and retry. This disables the DLL injection and should resolve the issue.
  • Analysis will fail when using an old (Python 2 based) CCT or project. See Python 3 Migration for details on how to upgrade your CCT or project.